Completeness of records
| Characteristic Name: | Completeness of records |
| Dimension: | Completeness |
| Description: | Every real world entity instance, that is relevant for the organization can be found in the data |
| Granularity: | Record |
| Implementation Type: | Process-based approach |
| Characteristic Type: | Usage |
Verification Metric:
| The number of tasks failed or under performed due to missing records |
| The number of complaints received due to missing records |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Implement a process level validation mechanism to avoid occurrence of missing records | (1) A buyer must record/verify an expense or asset in accordance with accepting/receiving any purchased items. (2)New application are stored in a temporary cabinet after entering into the system and they will be transferred to the file cabinet at the end of every week after the property manager cross check them with the system |
| Execute database commits upon transaction sequences in application programs and make sure all the transactions in the sequence successfully commit and generate the required records at the end of the sequence. | (1) In generating the MRP, the database operations will not be committed unless all materials in BOM is successfully executed for MRP |
| When distributed databases are used or online data collection devices are used, ensure the synchronisation/replication of records happen successfully without distortions and omissions. | (1) EFTPOS transactions are replicated with bank database and create the new balance B/F in the account |
| Implement periodic audit process for critical tangible objects that are recorded as data in database | (1) Annual audit for tangible assets in the organisation |
| Implement a validation mechanism in data transfers considering the business rules to monitor and ensure all records relevant to a event/transaction is transferred successfully. | (1) Rules to verify the number of records in the source file and destination file (2) All records relevant to a customer trip is transferred to the central database from online data stores |
| Maintain error logs for system transactions and regularly monitor them and perform relevant forensic activities to find missing records. | (1) A failed sales order creation |
Validation Metric:
| How mature is the process to prevent missing records |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| if Dept is a relation representing the employees of a given department, and one specific employee of the department is not represented as a tuple of Dept, then the tuple corresponding to the missing employee is in ref(Dept),and ref(Dept) differs from Dept in exactly that tuple. | C. Batini and M, Scannapieco, “Data Quality: Concepts, Methodologies, and Techniques”, Springer, 2006. |
| if a column should contain at least one occurrence of all 50 states, but the column contains only 43 states, then the population is incomplete. | Y. Lee, et al., “Journey to Data Quality”, Massachusetts Institute of Technology, 2006. |
| the database should contain all customers in North and South America, but it is known that the database reflects only a portion of the company’s customers. Coverage in this example is the percent- age of customers actually captured in the database compared to the population of all customers that should be in it. | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| A record exists for every Real-World Object or Event the Enterprise needs to know about. | ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
| Completeness of data refers to the extent to which the data collected matches the data set that was developed to describe a specific entity. Monitoring for incomplete lists of eligible records or missing data items will identify data quality problems. | HIQA 2011. International Review of Data Quality Health Information and Quality Authority (HIQA), Ireland. http://www.hiqa.ie/press-release/2011-04-28-international-review-data-quality. |
| Quality of having all data that existed in the possession of the sender at time the data message was created. | ISO 2012. ISO 8000-2 Data Quality-Part 2-Vocabulary. ISO. |
| Data is complete if no piece of information is missing – anti-example: "The Beatles were John Lennon, George Harrison and Ringo Starr" | KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published. |
| Every real-world phenomenon is represented. | PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a. |
Continuity of data access
| Characteristic Name: | Continuity of data access |
| Dimension: | Availability and Accessability |
| Description: | The technology infrastructure should not prohibit the speed and continuity of access to the data for the users |
| Granularity: | Information object |
| Implementation Type: | Process-bases approacd |
| Characteristic Type: | Usage |
Verification Metric:
| The number of tasks failed or under performed due to the lack of continuity in data access |
| The number of complaints received due to lack of continuity in data access |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Convenient and efficient platform should be made available to access data depending on the task at hand | (1) For a sales person, a web based interface run on a smart device is more suitable to quickly access data |
| Speed of the data retrieval should be acceptable for users working pace | (1) For an online customer care executive, speedy retrieval of information is necessary since the customer cannot be kept waiting (2) With the growth of the database reports become slower (Anti example) |
| Continuous and unobstructed connectivity should be ensured for data retrievals | (1) Connection lost while accessing reports (Anti example) |
| Proper concurrency control has been implemented | (1) Controlling access to data by locks |
| Technological changes in the infrastructure/system should be handled in such a way that they should not make data inaccessible | (1) New version of the software does not provide access to " X out orders" since the new version does not allow the function "X out" |
Validation Metric:
| How mature is the process of maintaining an infrastructure for data access |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| 1) For example, recording the age and race in medical records may be appropriate.
However, it may be illegal to collect this information in human resources departments. 2) For example, the best and easiest method to obtain demographic information may be to obtain it from an existing system. Another method may be to assign data collection by the expertise of each team member. For example, the admission staff collects demographic data, the nursing staff collects symptoms, and the HIM staff assigns codes. Team members should be assigned accordingly. |
B. Cassidy, et al., “Practice Brief: Data Quality Management Model” in Journal of AHIMA, 1998, 69(6). |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| 1) Is there a continuous and unobstructed way to get to the information?
2) Can the infrastructure match the user’s working pace? |
EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer. |
| Data is easy and quick to retrieve. | PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a. |
| 1) availability of a data source or a system.
2) Accessibility expresses how much data are available or quickly retrievable. 3) The frequency of failures of a system, its fault tolerance. |
SCANNAPIECO, M. & CATARCI, T. 2002. Data quality under a computer science perspective. Archivi & Computer, 2, 1-15. |